Skip to content

fix(arrow/extensions): reject Null Variant typed_value - #1243

Open
dgvj-work wants to merge 1 commit into
apache:mainfrom
dgvj-work:fix/variant-null-typed-value
Open

fix(arrow/extensions): reject Null Variant typed_value#1243
dgvj-work wants to merge 1 commit into
apache:mainfrom
dgvj-work:fix/variant-null-typed-value

Conversation

@dgvj-work

@dgvj-work dgvj-work commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Rationale for this change

A Null typed_value column is not a valid shredded Variant type. Nulls are encoded in the value column as Variant null (00). A dedicated Null typed_value would also make “field present and null” indistinguishable from “field missing” for shredded objects.

See apache/arrow#50622 and apache/arrow#50810.

Fixes #1205

What changes are included in this PR?

  • NewVariantType rejects a Null typed_value field
  • Nested shredded fields with a Null typed_value are also rejected

Are these changes tested?

  • go test ./arrow/extensions

Are there any user-facing changes?

Yes — constructing a Variant extension type with a Null typed_value now returns arrow.ErrInvalid.

A Null typed_value column is not a valid shredded type. Variant nulls
belong in the value column.

Fixes apache#1205

Signed-off-by: Digvijay <digvijay.vaghela@yahoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Parquet] Variant Null type typed_value field is supported

1 participant